Managing content across discrete systems

ABSTRACT

Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content across discrete systems. A content management system can be implemented to manage content items and synchronize content items across devices. A content collaboration system can be implemented to generate documents and facilitate collaboration on documents. To take advantage of the content management system&#39;s functionality to manage and synchronize content items while also providing the collaboration functionality of the content collaboration system, the content management system can store and manage references to documents created in the content collaboration system. The document references can be managed by the content management system such that the document references appear to users as if the document references were the referenced document in the collaboration system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. application Ser. No.14/978,653, filed Dec. 22, 2015, which is hereby incorporated byreference in its entirety.

BACKGROUND

Migrating data and software from one system to another system can oftenbe complicated. The volume of data, complexity of the file structure,and/or the complexity of the software configuration on the first systemcan make moving data and software to the second system very risky.Moreover, merging the two systems into a single system can becomplicated and prone to problems as the two systems may not work welltogether once merged.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for managing content across discrete systems. A contentmanagement system can be implemented to manage content items andsynchronize content items across devices. A content collaboration systemcan be implemented to generate documents and facilitate collaboration ondocuments. To take advantage of the content management system'sfunctionality to manage and synchronize content items while alsoproviding the collaboration functionality of the content collaborationsystem, the content management system can store and manage references todocuments created in the content collaboration system. A reference canbe a content item managed by the content management system that includesan identifier for the referenced document, but does not include thecontent of the referenced document.

When metadata for a document in the content collaboration systemchanges, the content management system can synchronize the updatedmetadata with client devices so that the metadata for the correspondingreferences matches the metadata for the document in the contentcollaboration system. Similarly, when a document is deleted from thecontent collaboration system, the content management system can deletereferences to the deleted document from client devices. Users caninteract with references in the content management system just likeother content items. For example, a user can select a reference to causethe user's device to present the corresponding document in the contentmanagement system. Thus, to users of the content management system, thereference appears to be the referenced document.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the disclosurewill become apparent by reference to specific embodiments thereof whichare illustrated in the appended drawings. Understanding that thesedrawings depict only example embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 shows an example configuration of devices and a network inaccordance with some embodiments;

FIG. 2 illustrates an example system for managing content acrossdiscrete systems;

FIG. 3 is a block diagram of an example system for synchronizingdocument reference metadata in a content management system with documentmetadata in a collaboration system;

FIG. 4 is a block diagram of an example system for synchronizingdocument metadata in a collaboration system with document referencemetadata in a content management system;

FIG. 5 is a block diagram of an example system for deleting referencesto a document in the collaboration system from the content managementsystem when document is deleted from collaboration system;

FIG. 6 is a flow diagram of an example process for synchronizing changesmade to documents in collaboration system with references managed bycontent management system;

FIG. 7 is a flow diagram of an example process for synchronizing changesmade to document references managed by content management system 106with documents in collaboration system;

FIG. 8A shows an example possible system embodiment for implementingvarious embodiments of the present technology; and

FIG. 8B shows an example possible system embodiment for implementingvarious embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses the need in the art for a safe andconvenient way to migrate and/or merge data and/or software configuredon one system to another system.

With respect to implementing various embodiments of the disclosedtechnology, an example system configuration 100 is shown in FIG. 1,wherein electronic devices communicate via a network for purposes ofexchanging content and other data. The system can be configured for useon a wide area network such as that illustrated in FIG. 1. However, thepresent principles are applicable to a wide variety of networkconfigurations that facilitate the intercommunication of electronicdevices. For example, each of the components of system 100 in FIG. 1 canbe implemented in a localized or distributed fashion in a network.

In system 100, a user can interact with content management system 106(e.g., an online synchronized content management system) through clientdevices 102 ₁, 102 ₂, . . . , 102 _(n) (collectively “102”) connected tonetwork 104 by direct and/or indirect communication. Content managementsystem 106 can support connections from a variety of different clientdevices, such as: desktop computers; mobile computers; mobilecommunications devices, e.g. mobile phones, smart phones, tablets; smarttelevisions; set-top boxes; and/or any other network enabled computingdevices. Client devices 102 can be of varying type, capabilities,operating systems, etc. Furthermore, content management system 106 canconcurrently accept connections from and interact with multiple clientdevices 102.

A user can interact with content management system 106 via a client-sideapplication installed on client device 102 _(i). In some embodiments,the client-side application can include a content management systemspecific component. For example, the component can be a stand-aloneapplication, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 106 via a third-party application, such as a web browser, thatresides on client device 102 _(i) and is configured to communicate withcontent management system 106. In either case, the client-sideapplication can present a user interface (UI) for the user to interactwith content management system 106. For example, the user can interactwith the content management system 106 via a client-side applicationintegrated with the file system or via a webpage displayed using a webbrowser application.

Content management system 106 can enable a user to store content, aswell as perform a variety of content management tasks, such as retrieve,modify, browse, and/or share the content. Furthermore, contentmanagement system 106 can enable a user to access the content frommultiple client devices 102. For example, client device 102 _(i) canupload content to content management system 106 via network 104. Later,the same client device 102 _(i) or some other client device 102 _(j) canretrieve the content from content management system 106.

To facilitate the various content management services, a user can createan account with content management system 106. User account database 150can maintain the account information. User account database 150 canstore profile information for registered users. In some cases, the onlypersonal information in the user profile can be a username and/or emailaddress. However, content management system 106 can also be configuredto accept additional user information such as birthday, address, billinginformation, etc.

User account database 150 can include account management information,such as account type (e.g. free or paid), usage information, (e.g. fileedit history), maximum storage space authorized, storage space used,content storage locations, security settings, personal configurationsettings, content sharing data, etc. Account management module 124 canbe configured to update and/or obtain user account details in useraccount database 150. The account management module 124 can beconfigured to interact with any number of other modules in contentmanagement system 106.

An account can be used to store content, such as digital data,documents, text files, audio files, video files, etc., from one or moreclient devices 102 authorized on the account. The content can alsoinclude collections for grouping content items together with differentbehaviors, such as folders, playlists, albums, etc. For example, anaccount can include a public folder that is accessible to any user. Thepublic folder can be assigned a web-accessible address. A link to theweb-accessible address can be used to access the contents of the publicfolder. In another example, an account can include: a photos collectionthat is intended for photos and that provides specific attributes andactions tailored for photos; an audio collection that provides theability to play back audio files and perform other audio relatedactions; or other special purpose collection. An account can alsoinclude shared collections or group collections that are linked with andavailable to multiple user accounts. The permissions for multiple usersmay be different for a shared collection.

The content can be stored in content storage 160. Content storage 160can be a storage device, multiple storage devices, or a server.Alternatively, content storage 160 can be a cloud storage provider ornetwork storage accessible via one or more communications networks.Content management system 106 can hide the complexity and details fromclient devices 102 so that client devices 102 do not need to knowexactly where or how the content items are being stored by contentmanagement system 106. In some embodiments, content management system106 can store the content items in the same collection hierarchy as theyappear on client device 102 _(i). However, content management system 106can store the content items in its own order, arrangement, or hierarchy.Content management system 106 can store the content items in a networkaccessible storage (NAS) device, in a redundant array of independentdisks (RAID), etc. Content storage 160 can store content items using oneor more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4,HFS/HFS+, BTRFS, and so forth.

Content storage 160 can also store metadata describing content items,content item types, and the relationship of content items to variousaccounts, collections, or groups. The metadata for a content item can bestored as part of the content item or can be stored separately. In onevariation, each content item stored in content storage 160 can beassigned a system-wide unique identifier.

Content storage 160 can decrease the amount of storage space required byidentifying duplicate content items or duplicate segments of contentitems. Instead of storing multiple copies, content storage 160 can storea single copy and then use a pointer or other mechanism to link theduplicates to the single copy. Similarly, content storage 160 can storecontent items more efficiently, as well as provide the ability to undooperations, by using a content item version control that tracks changesto content items, different versions of content items (includingdiverging version trees), and a change history. The change history caninclude a set of changes that, when applied to the original content itemversion, produce the changed content item version.

Content management system 106 can be configured to support automaticsynchronization of content from one or more client devices 102. Thesynchronization can be platform agnostic. That is, the content can besynchronized across multiple client devices 102 of varying type,capabilities, operating systems, etc. For example, client device 102_(i) can include client software, which synchronizes, via asynchronization module 132 at content management system 106, content inclient device 102 _(i)'s file system with the content in an associateduser account. In some cases, the client software can synchronize anychanges to content in a designated collection and its sub-collections,such as new, deleted, modified, copied, or moved content items orcollections. The client software can be a separate software application,can integrate with an existing content management application in theoperating system, or some combination thereof. In one example of clientsoftware that integrates with an existing content managementapplication, a user can manipulate content items directly in a localcollection, while a background process monitors the local collection forchanges and synchronizes those changes to content management system 106.Conversely, the background process can identify content that has beenupdated at content management system 106 and synchronize those changesto the local collection. The client software can provide notificationsof synchronization operations, and can provide indications of contentstatuses directly within the content management application. Sometimesclient device 102 _(i) may not have a network connection available. Inthis scenario, the client software can monitor the linked collection forcontent item changes and queue those changes for later synchronizationto content management system 106 when a network connection is available.Similarly, a user can manually start, stop, pause, or resumesynchronization with content management system 106.

A user can view or manipulate content via a web interface generated andserved by user interface module 122. For example, the user can navigatein a web browser to a web address provided by content management system106. Changes or updates to content in the content storage 160 madethrough the web interface, such as uploading a new version of a contentitem, can be propagated back to other client devices 102 associated withthe user's account. For example, multiple client devices 102, each withtheir own client software, can be associated with a single account andcontent items in the account can be synchronized between each of themultiple client devices 102.

Content management system 106 can include a communications interface 120for interfacing with various client devices 102, and can interact withother content and/or service providers 109 ₁, 109 ₂, . . . , 109 _(n)(collectively “109”) via an Application Program Interface (API). Certainsoftware applications can access content storage 160 via an API onbehalf of a user. For example, a software package, such as an apprunning on a smartphone or tablet computing device, can programmaticallymake calls directly to content management system 106, when a userprovides credentials, to read, write, create, delete, share, orotherwise manipulate content. Similarly, the API can allow users toaccess all or part of content storage 160 through a web site.

Content management system 106 can also include authenticator module 126,which can verify user credentials, security tokens, API calls, specificclient devices, and so forth, to ensure only authorized clients andusers can access content items. Further, content management system 106can include analytics module 134 module that can track and report onaggregate file operations, user actions, network usage, total storagespace used, as well as other technology, usage, or business metrics. Aprivacy and/or security policy can prevent unauthorized access to userdata stored with content management system 106.

Content management system 106 can include sharing module 130 formanaging sharing content publicly or privately. Sharing content publiclycan include making the content item accessible from any computing devicein network communication with content management system 106. Sharingcontent privately can include linking a content item in content storage160 with two or more user accounts so that each user account has accessto the content item. The sharing can be performed in a platform agnosticmanner. That is, the content can be shared across multiple clientdevices 102 of varying type, capabilities, operating systems, etc. Thecontent can also be shared across varying types of user accounts.

In some embodiments, content management system 106 can be configured tomaintain a content directory identifying the location of each contentitem in content storage 160. The content directory can include a uniquecontent entry for each content item stored in the content storage.

A content entry can include a content path that can be used to identifythe location of the content item in a content management system. Forexample, the content path can include the name of the content item and afolder hierarchy associated with the content item. For example, thecontent path can include a folder or path of folders in which thecontent item is placed as well as the name of the content item. Contentmanagement system 106 can use the content path to present the contentitems in the appropriate folder hierarchy.

A content entry can also include a content pointer that identifies thelocation of the content item in content storage 160. For example, thecontent pointer can include the exact storage address of the contentitem in memory. In some embodiments, the content pointer can point tomultiple locations, each of which contains a portion of the contentitem.

In addition to a content path and content pointer, a content entry canalso include a user account identifier that identifies the user accountthat has access to the content item. In some embodiments, multiple useraccount identifiers can be associated with a single content entryindicating that the content item has shared access by the multiple useraccounts.

To share a content item privately, sharing module 130 can be configuredto add a user account identifier to the content entry associated withthe content item, thus granting the added user account access to thecontent item. Sharing module 130 can also be configured to remove useraccount identifiers from a content entry to restrict a user account'saccess to the content item.

To share content publicly, sharing module 130 can be configured togenerate a custom network address, such as a uniform resource locator(URL), which allows any web browser to access the content in contentmanagement system 106 without any authentication. To accomplish this,sharing module 130 can be configured to include content identificationdata in the generated URL, which can later be used to properly identifyand return the requested content item. For example, sharing module 130can be configured to include the user account identifier and the contentpath in the generated URL. Upon selection of the URL, the contentidentification data included in the URL can be transmitted to contentmanagement system 106 which can use the received content identificationdata to identify the appropriate content entry and return the contentitem associated with the content entry.

In addition to generating the URL, sharing module 130 can also beconfigured to record that a URL to the content item has been created. Insome embodiments, the content entry associated with a content item caninclude a URL flag indicating whether a URL to the content item has beencreated. For example, the URL flag can be a Boolean value initially setto 0 or false to indicate that a URL to the content item has not beencreated. Sharing module 130 can be configured to change the value of theflag to 1 or true after generating a URL to the content item.

In some embodiments, sharing module 130 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing module 130 can be configured to only return a content itemrequested by a generated link if the URL active flag is set to 1 ortrue. Thus, access to a content item for which a URL has been generatedcan be easily restricted by changing the value of the URL active flag.This allows a user to restrict access to the shared content item withouthaving to move the content item or delete the generated URL. Likewise,sharing module 130 can reactivate the URL by again changing the value ofthe URL active flag to 1 or true. A user can thus easily restore accessto the content item without the need to generate a new URL.

While content management system 106 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 106 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible.

FIG. 2 illustrates an example system 200 for managing content acrossdiscrete systems. For example, system 200 can be configured to managesynchronization, distribution, and/or access to documents ofcollaboration system 222 on collaboration server 220 using references tothe documents managed by content management system 106 of contentmanagement server 210. For example, content management server 210 can bea computing device or computing devices configured to run software ofcontent management system 106, as described above with reference to FIG.1.

The term “document” is used herein as a convenient way to distinguish acontent item created, managed, and/or stored by collaboration system 222from content items managed by content management system 106, asdescribed above. A “document” can be any type of content item (e.g.,file, image, word processing file, a presentation, a spreadsheet, abundle of files, etc.). The term “reference” is used herein to refer toa content item managed by content management system 106 that includes areference to a document of collaboration system 222. For example, thereference can be a file that includes a unique identifier (e.g., anumber, sequence of characters and numbers, etc.) for the correspondingdocument in collaboration system 222. The file can have a unique fileextension (e.g., file.ref, file.paper. file.note, etc.) that identifiesthe file as a reference to a document in collaboration system 222.Unless otherwise stated, the description below assumes that all usersdescribed herein have accounts with both content management system 106and collaboration system 222 and are logged into the respectiveaccounts.

In some embodiments, system 200 can include collaboration server 220.For example, collaboration server 220 can be a computing device orcomputing devices configured to run software of collaboration system222. Collaboration system 222 can be software (e.g., a web server,collaboration server, document editor, etc.) configured on collaborationserver 220 that allows users of collaboration system 222 to collaborateon creating, editing, and/or otherwise manipulating documents. Forexample, a user of user device 230 can invoke web browser 232 andnavigate to collaboration server 220 using well-known mechanisms. Forexample, user device 230 can correspond to client device 102 _(i) ofFIG. 1.

Creating Documents

In some embodiments, web browser 232 can receive web page 233 fromcollaboration system 222 that allows the user to create, modify, delete,rename, etc., documents (e.g., document 224) managed by collaborationsystem 222. For example, the user can provide input to web page 233through web browser 232 to create a new document in collaboration system222. In response to receiving the user input, web browser 232 can send arequest to collaboration system 222 to create document 224. When therequest is received, collaboration system 222 can create document 224and/or document metadata 226 corresponding to document 224. For example,document metadata 226 can be stored in document 224. Document metadata226 can be stored separately from document 224 (e.g., as a distinct fileor object).

In some embodiments, web browser 232 can receive user input to savedocument 224. For example, web page 233 received from collaborationsystem 222 and presented by web browser 232 on user device 230 canpresent an option to save document 224 in content management system 106.Upon receiving user input selecting the save option, web browser 232 canpresent a graphical user interface (e.g., file system browser) thatallows the user to specify a location (e.g., file system location,specific folder, etc.) in the user's account on content managementsystem 106 where the document should be stored. After the user hasprovided input specifying the location where the document should bestored, web browser 232 can send the location to collaboration system222.

In some embodiments, upon receiving the save location, collaborationsystem 222 can save the current state of document 224. For example,collaboration system 222 can save the contents of document 224 and/ordocument metadata 226. If document 224 has been modified, collaborationsystem 222 can, for example, save a timestamp indicating the time whendocument 224 was last modified in document metadata 226. If the userprovided a new name for document 224 when specifying the save location,collaboration system 222 can rename document 224 according to the newname.

In some embodiments, upon receiving the save location, collaborationsystem 222 can send a request to content management system 106 togenerate a reference for document 224. For example, if document 224 is anew document, then a new reference 212 can be created on contentmanagement system 106 for the new document. The new reference requestcan include the new name for document 224, the user-specified location(e.g., document save location) where the reference should be stored, aunique identifier for document 224, and/or metadata 226 for document224, for example.

In some embodiments, upon receiving the new reference request, contentmanagement system 106 can generate a new reference to document 224. Forexample, content management system 106 can create document reference 212having the same name as document 224. Content management system 106 canstore or save reference 212 in the requesting user's account of contentmanagement system 106 at the user-specified location in the request.Content management system 106 can store the received document metadata226 as reference metadata 214. For example, reference metadata 214 canbe stored in document reference 214. Reference metadata 214 can bestored separately (e.g., as a distinct file or object) from documentreference 212.

In some embodiments, content management system 106 can generatereference map 228. For example, reference map 228 can include data thatmaps or associates the identifier for document 224 to user accounts andlocations where references to document 224 exist within contentmanagement system 106. For example, once document 224 and correspondingdocument reference 212 are created, the user of user device 230 canshare document reference 212 just like any other content item in contentmanagement system 106. Each time a new reference to document 224 iscreated (e.g., copied, shared, added, etc.) in content management system106 (e.g., by the user of user device 230 or by another user), contentmanagement system 106 can add a new mapping identifying the documentreferenced, the user account associated with the new reference, and thelocation of the new reference in the user account (e.g.,“docID:user1:/home/folder1/doc.paper”).

In some embodiments, reference map 228 can be a database that storesreference mappings for all documents in collaboration system 224. Insome embodiments, reference map 228 can correspond to a single document(e.g., document 224). For example, content management system 106 canstore a distinct reference map 228 for each document in collaborationsystem 222 that identifies user accounts and locations where referencesexist within content management system 106 that correspond to a specificdocument. For example, reference map 228 can identify user accounts andlocations for references to document 224 only. For example, whilereference 212 includes an identifier that allows content managementsystem 106 to identify corresponding document 224 to collaborationsystem 222, reference map 228 includes information that allows contentmanagement system 106 to locate references to document 224 withincontent management system 106.

In some embodiments, content management system 106 can synchronizedocument reference 212 with user device 230. As described above withreference to FIG. 1, content management system 106 provides mechanismsto manage and synchronize content items with user devices. Sincereference 212 and/or reference metadata 214 are content items managed bycontent management system 106, these content items can be synchronizedwith client device 230 in the same way as described above with referenceto FIG. 1.

In some embodiments, content management system 106 can send reference212 and metadata 214 to content management system (CMS) client 234(e.g., client-side application of FIG. 1) on user device 230. CMS client234 can store document reference 212 as document reference 242, forexample, in file system 240 of user device 230. For example, file system240 can be a local file system managed by content management system 106and/or CMS client 234. Similarly, CMS client 234 can store referencemetadata 244 corresponding to reference 242 in file system 240 of userdevice 230.

In some embodiments, CMS client 234 can store a local copy of document224 in local cache 250. For example, cache 250 can be a hidden cache ofdocuments corresponding to document references stored in file system240. Cache 250 can be stored within file system 240. Cached document 252can correspond to document reference 242, for example. For example, whena user selects document reference 240 and opens document 224, asdescribed below, CMS client 234 can store a local copy of document 224and document metadata 226 in cache 250 as document 252 and documentmetadata 256, respectively. In some embodiments, CMS client 234 canautomatically request the current version of document 224 fromcollaboration system 222 when a new document reference 242 or updatedmetadata 244 is received by CMS client 234 from content managementsystem 106. Thus, the user of user device 230 can still view documentsof collaboration system 222 even when user device 230 is offline (e.g.,not connected to network 104).

In some embodiments, cache 250 can be a read-only cache. For example,when the user of user device 230 opens document 252, the user may viewthe document but may not be able to edit the document. In someembodiments, cache 250 can be a read-write cache that allows the user toboth view and edit document 252. In some embodiments, cache 250 caninclude document metadata 256 corresponding to document 252. Thus, whena user opens document 252, the corresponding metadata 256 can be readand a graphical user interface can be presented that presents themetadata for document 256.

Opening a Document Using CMS Native Client

In some embodiments, a user can open document 224 managed bycollaboration system 222 through CMS client 234 by selecting documentreference 242 stored on user device 242. For example, CMS client 234 canbe a native client specifically built for the operating environment(e.g., operating system, device specifications, etc.) of user device230. For example, a user can browse the local file system 240 on userdevice 230 using a well-known file browser or other operating systemfile browser. The user can locate document reference 242 within filesystem 240 and provide user input to user device 230 selecting documentreference 242. Upon receipt of the user input selecting documentreference 242, user device 230 (e.g., the operating system of userdevice 230) can invoke CMS client 234. For example, document reference242 can have a file extension (e.g., .ref, .paper, .notes, etc.)associated with CMS client 234. The operating system of user device 230can be configured to invoke CMS client 234 when a file with theappropriate extension is selected by a user, for example.

In some embodiments, CMS client 234 can open document 224 oncollaboration system 222. For example, when the operating system of userdevice 230 invokes CMS client 234, the operating system can providedocument reference 242 to CMS client 234. The operating system can, forexample, provide the file system path for document reference 242 to CMSclient 234 as a parameter to the invocation of CMS client 234. Uponreceiving document reference 242, CMS client 234 can determine thatdocument reference 242 is a reference to document 224 on collaborationsystem 222 and present document 224 on a display of user device 230.

In some embodiments, CMS client 234 can open document 224 oncollaboration server 220. For example, when CMS client 234 determinesthat user device 230 is connected to network 104 (e.g., the Internet, aLAN, a WAN, etc.), then CMS client 234 can invoke collaboration client236 to present document 224 on a display of user device 230. In someembodiments, collaboration client 236 can be a web client viewed throughan internal web browser of CMS client 234. For example, CMS client 234can obtain a document identifier from document reference 242. In someembodiments, CMS client 234 can invoke a web browser and pass a URL(e.g., “http://www.collaborator.com/editor/12345”) that includes anaddress for collaboration system 222 (e.g.,“http://www.collaborator.com”) and the identifier (e.g., “12345”) fordocument 224. The web browser can use the URL to obtain a web page forthe web client (e.g., collaboration client 236) from collaborationsystem 222 that presents document 224. The user can then view or editdocument 224 using various features of the web client.

In some embodiments, CMS client 234 can open document 252 on user device230. For example, when CMS client 234 determines that user device 230 isnot connected to network 104 (e.g., the Internet, a LAN, a WAN, etc.),then CMS client 234 can invoke collaboration client 236 to presentdocument 252 on a display of user device 230. In some embodiments,collaboration client 236 can be an internal document viewer of CMSclient 234. For example, collaboration client 236 can open document 252and/or document metadata 256 locally and provide a read-only view ofdocument 252 so that a user can view the contents of document 224 (e.g.,represented by document 252) even when user device 230 is offline.

Opening a Document Using CMS Web Client

In some embodiments, a user can open document 224 managed bycollaboration system 222 through a web client (e.g., web page) ofcontent management system 106 presented by web browser 232. For example,the user can invoke web browser 232 and navigate through network 104 tocontent management system 106. Web browser 232 can receive a web pagefrom content management system 106 that presents content itemsassociated the user's account and managed by content management system106. For example, the web page can include a representation of documentreference 212 and reference metadata 214.

In some embodiments, upon receiving user input selecting documentreference 212 on the web page, web browser 232 can send the selection tocontent management system 106. For example, upon receiving the selectionof document reference 212, content management system 106 can determinethat the selected content item is a collaboration document reference(e.g., based on the file extension, content item type, etc.) andredirect web browser 232 to collaboration system 222. For example,content management system 106 can send web browser 232 a URL thatspecifies an address for collaboration server 220 and identifiesdocument 224, as described above. For example, the redirection can causeweb browser 232 to receive collaboration system web page 233 for viewingand/or editing document 224. When web browser 232 receives web page 233,web browser 232 can present web page 233, including a representation ofthe contents of document 224 and/or metadata 226, on a display ofcomputing device 230 for editing and/or viewing.

Syncing Changes Made at Collaboration System

FIG. 3 is a block diagram of an example system 300 for synchronizingdocument reference metadata with document metadata. For example, system300 can correspond to system 200 of FIG. 2. In some embodiments, a userof user device 230 can interact with collaboration client 302 to viewand/or edit document 224 in collaboration system 222. For example,collaboration client 302 can be a web client presented by web browser232, such as collaboration web page 233. Collaboration client 302 cancorrespond to collaboration client 236.

In some embodiments, the user can interact with collaboration system 222through collaboration client 302 to change the name of document 224. Forexample, collaboration client 302 can present an option to renamedocument 224. The user can select the option to rename document 224 andprovide a new name for document 224. Upon receiving the new name,collaboration client 302 can send the new name to collaboration system222. When collaboration system 222 receives the new name, collaborationsystem 222 can rename document 224 according to the user-specified name.For example, collaboration system 222 can store the user-specified namein document metadata 226 corresponding to document 224 in collaborationsystem 222.

Similarly, the user can interact with collaboration system 222 throughcollaboration client 302 to change the location of document 224. Forexample, collaboration client 302 can present an option to move document224. The user can select the option to move document 224 and provide anew location (e.g., folder, file system path, etc.) within the user'saccount on content management system 106 for document 224. Uponreceiving the new location, collaboration client 302 can send the newlocation to collaboration system 222. When collaboration system 222receives the new location, collaboration system 222 can store the newlocation for document 224 in document metadata 226 corresponding todocument 224 in collaboration system 222.

In some embodiments, the user can cause document metadata 226 to changeby editing document 224. For example, document metadata 226 can includea timestamp indicating when the most recent modification (e.g., edit) todocument 224 occurred. When the user uses collaboration client 302 toedit document 224, collaboration system 222 will update this “lastmodified” timestamp in document metadata 226 to reflect the date andtime of the latest modification to document 224.

In some embodiments, collaboration system 222 can send metadata updatesto content management server 106. For example, collaboration system 222can detect when a change to document metadata 226 occurs. Whencollaboration system 222 detects a change to document metadata 226,collaboration system 222 can send metadata update message 320 to contentmanagement server 106. For example, metadata update message 320 caninclude the unique collaboration system identifier for document 224 andany changes to document metadata 226. For example, if the name, locationand/or last modified timestamp in document metadata 226 has changed,metadata update message 320 can include the new name, the new locationand/or the new timestamp.

In some embodiments, content management system 106 can update documentreference metadata to reflect document changes received in metadataupdate message 320. For example, content management system 106 candetermine which document references need to be updated in response toreceiving metadata update message 320 based on the document identifierin metadata update message 320. Content management system 106 can, forexample, compare the document identifier in message 320 to reference map228 to determine the user accounts and locations of references todocument 224. For example, a copy of reference 212 may have been sharedwith multiple user accounts and the each user account may store a copyof reference 212 in a different location. Reference map 228 provides amechanism by which content management server 106 can find the variouscopies of document reference 212 in content management system 106.

After content management system 106 determines the locations ofreferences (e.g., reference 212) corresponding to document 224, contentmanagement system 106 can update the metadata (e.g., metadata 214) foreach reference (e.g., reference 212) associated with document 224 toreflect the changes to document metadata 226. Reference metadata 214 canthen be used to present a representation of document reference 212having the new name, location, and/or last modified timestamp on a webclient of content management system 106. Thus, the representation ofdocument reference 212 on the graphical user interface of the web clientwill appear as if it is document 224 when viewed by a user.

In some embodiments, content management server 106 can synchronizereference metadata with client devices. For example, since referencemetadata 214 is a content item managed by content management server 106,content management server 106 can synchronize reference metadata 214managed by content management system 106 with reference metadata 244 onuser device 230. For example, content management server 106 can send areference update message 324 that identifies document reference 242 andcontains information describing the changes to reference metadata 214.

If reference update 324 includes information indicating that the name ofdocument 224 has changed, then CMS client 234 can change the name ofdocument reference 242 on user device 230. If reference update 324includes information indicating that the location of document 224 haschanged, then CMS client 234 can move document reference 242 to a newlocation within file system 240 on user device 230. If reference update324 includes information indicating that the last modified timestamp ofdocument 224 has changed, then CMS client 234 can update the lastmodified timestamp of document reference 242 so that the correcttimestamp is presented when document reference 242 is viewed in filesystem 240 on user device 230.

In some embodiments, system 300 can include user device 310. Forexample, user device 310 can be a device of another user (e.g., seconduser) with which document reference 212 has been shared. The user (e.g.,first user) of user device 230 may have, for example, sent documentreference 212 to the second user in an email message, instant message,or using some other electronic communication mechanism. The user of userdevice 310 can have a user account with content management system 106.The second user can save document reference 212 as document reference314 on user device 310 in a file system of user device 310 managed bycontent management system 106.

Upon detecting the new content item in the managed file system, CMSclient 312 can synchronize document reference 314 and/or referencemetadata 316 with the user's account on content management system 106.When content management system 106 detects another copy of documentreference 212 and/or reference metadata 214 in content management system106, content management system 106 can update reference map 228 to mapthe user account and location of the new document reference to document224, as described above. When changes to document reference 212 and/orreference metadata 214 received in metadata update message 320 fromcollaboration system 222, content management system 106 can synchronizethe changes with user device 310 in the same way as changes aresynchronized with user device 230, as described above. For example,content management system 106 can update the reference to document 224in the second user's account on content management system 106 and sendreference update message 322 to CMS client 312. For example, referenceupdate message 322 can include an identifier (e.g., path and/or filename) for document reference 314 and describe the changes (e.g., newname, new location, new last modified timestamp, etc.) to the metadatafor the reference to document 224 in the user's account.

Upon receiving reference update message 322, CMS client 312 on userdevice 310 can update document reference 314 and/or reference metadata316 with the metadata changes described in reference update message 322.For example, CMS client 312 can rename document reference 314 to the newname specified by the user of user device 230 and described in referenceupdate message 322. CMS client 312 can move document reference 314 to anew file system location (e.g., new folder, new director, etc.)specified by the user of user device 230 and described in referenceupdate message 322. Thus, when the user (e.g., the second user) of userdevice 310 views or browses for document reference 314 in a file browseron user device 310, document reference 314 will be presented to the userwith new name and/or at the new location specified by the user (e.g.,the first user) of user device 230.

Syncing Changes Made at Client Device

FIG. 4 is a block diagram of an example system 400 for synchronizingdocument metadata with document reference metadata. In some embodiments,a user can make changes to metadata 226 of document 224 in collaborationsystem 222 by modifying metadata 244 of document reference 242 on userdevice 230. For example, the user can browse file system 240 of FIG. 2using a file browser on user device 230. The user can view arepresentation of document reference 242 and/or reference metadata 244through the file browser. For example, the file browser can present arepresentative image for document reference 242. The file browser canpresent the name of document reference 242. The file browser can presentsome or all of metadata 242 for document reference 242, such as a lastmodified time, a list of users document 224 (or reference 212) has beenshared with, and/or other metadata.

In some embodiments, the user may change reference metadata 244 throughthe file browser. For example, the user may provide input to cause thefile browser on user device 230 to perform a rename operation ondocument reference 242 on user device 230 using the file browser. Theuser may provide input to cause the file browser on user device 230 toperform a move operation to move document reference 242 to anotherdirectory or folder in file system 240 on user device 230. After themove or rename operation is performed, the file browser can store thenew name and/or new location in reference metadata 244.

In some embodiments, CMS client 234 on user device 230 can updatereference metadata 214 on content management server 106 when referencemetadata 244 has been modified on user device 230. For example, CMSclient 234 can monitor file system 240 on user device 230 and detectchanges to content items (e.g., including document reference 242 and/orreference metadata 244) in file system 240. When CMS client 234 detectschanges to reference metadata 244, CMS client 234 can sendsynchronization message 402 to content management system 106.Synchronization message 402 can, for example, describe the changes theuser made to reference metadata 244, such as changes to the name and/orlocation of document reference 242 within file system 240, as describedabove. Upon receiving synchronization message 402, content managementsystem 106 can update reference metadata 214 with the metadata changesdescribed in synchronization message 402.

Alternatively, the user of user device 230 can modify reference metadata214 directly using web browser 232. For example, the user can used webbrowser 232 to navigate to a web page of content management system 106.The web page can present the content items in the user's account oncontent management system 106, such as document reference 212. The webpage can present some or all of the data in reference metadata 214 whenpresenting document reference 212. For example, the metadata presentedfor document reference 212 can include a name for document reference 212(e.g., document 224), a last modified timestamp for document 244, alocation for document reference 212, and/or other metadata for documentreference 212 and/or document 244.

In some embodiments, the user can provide input to web browser 232 tochange metadata associated with document reference 212. For example, theuser can provide input to the web page of content management system 106to change the name and/or location of document reference 212. Inresponse to receiving the user input, web browser 232 can send the newname and/or location for document reference 211 to content managementsystem 106. Upon receipt of the new name and/or location, contentmanagement system can update reference metadata 214 with the new nameand/or location for document reference 211.

In some embodiments, content management system 106 can send changeddocument metadata to collaboration system 222. For example, uponreceiving changes or modifications to document reference 212 and/orreference metadata 214, content management system 106 can send documentupdate message 404 describing changes made to document reference 212and/or reference metadata 214 to collaboration system 222. Documentupdate message 404 can include, for example, the identifiercorresponding to document 244 and a description of the metadata changesto be applied to document metadata 226 (e.g., the new user-specifiedname and/or location for document 224). Upon receipt of document update404, collaboration system 222 can identify and/or locate document 244based on the document identifier and update the document metadata 226.

In some embodiments, collaboration system 222 can cause contentmanagement system 106 to update document references in response toreceiving changes to document 224 and/or document metadata 226. Asdescribed above with reference to FIG. 3, collaboration system 222 cansend metadata update 320 to content management system 106 describingchanges made to document metadata 226. Metadata update message 320 caninclude the unique identifier for document 224 and a description ofchanges made to document metadata 226 (e.g., the new name, the newlocation, etc.).

In some embodiments, content management system 106 can update referencesto document 224 based on metadata update message 320. For example,content management system 106 can use the document identifier inmetadata update message 320 to find the locations of all references todocument 244 in reference map 228. The document identifier can be usedas an index to find all of the user accounts and locations within useraccounts where a copy of document reference 212 exists within contentmanagement system 106, for example.

After content management system 106 determines where each reference todocument 224 is within content management system 106, content managementsystem 106 can update the metadata for each reference with the metadatachanges described in metadata update message 320. For example, contentmanagement system 106 can update each reference to document 224 (e.g.,update the metadata for the reference) with the name and/or locationchanges specified by the user of user device 230.

After the metadata changes are applied to each reference to document 224within content management system 106, content management system 322 cansend the metadata changes for references to document 224 to other userdevices, such as user device 310, in reference update message 322. Forexample, reference update message 322 can include an identifier fordocument reference 314 (e.g., current path and/or file name) and adescription of the metadata changes to be applied to reference metadata316. For example, reference update message 322 can include the new nameand/or location for document 224 specified by the user of user device230.

Upon receiving reference update message 322, CMS client 312 on userdevice 310 can update document reference 314 and/or reference metadata316 with the metadata changes described in reference update message 322.For example, CMS client 312 can rename document reference 314 to the newname specified by the user of user device 230 and described in referenceupdate message 322. CMS client 312 can move document reference 314 to anew file system location (e.g., new folder, new director, etc.)specified by the user of user device 230 and described in referenceupdate message 322. Thus, when the user (e.g., the second user) of userdevice 310 views or browses for document reference 314 in a file browseron user device 310, document reference 314 will be presented to the userwith new name and/or at the new location specified by the user (e.g.,the first user) of user device 230.

Deleting Documents

FIG. 5 is a block diagram of an example system 500 for deletingreferences to document 224 in collaboration system 222 when document 224is deleted from collaboration system 222. In some embodiments, contentmanagement system 106 can delete references to document 224 from contentmanagement system 106 and/or user devices (e.g., 230 and/or 310) whendocument 224 is deleted from collaboration system 222.

In some embodiments, user device 230 can delete document reference 242upon receiving user input indicating the user's intent to deletedocument reference 242. For example, rather than causing document 224 tobe deleted from collaboration system 222, user device 230 can deletedocument reference 242 and/or reference metadata 244 from user device230. Since document reference 242 and reference metadata 244 are contentitems managed by CMS client 234, CMS client 234 will send asynchronization update to content management system 106 which will causethese content items to be deleted from the user's account on contentmanagement system 106. For example, CMS client 234 can send deletedocument message 502 that identifies the corresponding documentreference 212 on content management system 106. Upon receiving message502, content management system 106 can delete the corresponding documentreference 212, delete corresponding metadata 214, and update referencemap 228 to remove the entry for document reference 212. Thus, in someembodiments, deleting a document reference only causes removal of thatspecific document reference (and corresponding metadata) from the user'sdevice and removal of the corresponding document reference (andcorresponding metadata) from the user's account on content managementsystem 106.

In some embodiments, deletion of a document reference on a user devicecan cause the deletion of the corresponding referenced document fromcollaboration system 222. For example, a user of user device 230 canprovide input to the file browser on user device 230 to delete documentreference 242. In response to receiving the input, user device 230 candelete document reference 242 and/or reference metadata 244. Sincedocument reference 242 and reference metadata 244 are content itemsmanaged by CMS client 234, CMS client 234 will send a synchronizationupdate to content management system 106 which will cause these contentitems to be deleted from the user's account on content management system106. For example, CMS client 234 can send delete document message 502that identifies the corresponding document reference 212 on contentmanagement system 106. Upon receiving message 502, content managementsystem 106 can delete the corresponding document reference 212, deletecorresponding metadata 214, and update reference map 228 to remove theentry for document reference 212.

Upon deleting document reference 214 from content management system 106,content management system 106 can send delete document message 504 tocollaboration system 222 to cause collaboration system 222 to deletedocument 224 and corresponding document metadata 226. Message 504 can,for example, include the unique identifier for document 224. Uponreceiving message 504, collaboration system 222 can remove document 224and/or document metadata 226 from collaboration system 222.

Alternatively, the user of user device 230 can delete document 224through collaboration client 302. For example, the user can viewdocument 224 through collaboration client 302, as described above, andprovide input to collaboration client 302 to delete document 224 fromcollaboration system 222. Collaboration client 302 can invoke anprogramming interface of collaboration system 222 for deleting documentsfrom collaboration system 222 and provide the unique identifier fordocument 224 as a parameter to the invocation. Upon receiving the uniqueidentifier, collaboration system 222 can remove document 224 and/ordocument metadata 226 from collaboration system 222.

In some embodiments, deletion of a document from collaboration system222 causes all reference to the document to be deleted. For example,when collaboration system 222 removes document 224 from collaborationsystem 222, collaboration system 222 can send delete references message506 (e.g., a delete command, API invocation, etc.) to content managementsystem 106. Message 506 can include for, for example, the uniqueidentifier corresponding to document 224. When content management system106 receives delete references message 506, content management system106 can determine the locations of all references to document 224 incontent management system 106. For example, content management system106 can look up the locations of references to document 224 in referencemap 224 using the identifier for document 224 received in message 506.After the locations of each reference to document 224 are determinedusing reference map 228, content management system 106 can remove eachof the references to document 224 from content management system 106.Since the references (e.g., document reference 212) are content itemsmanaged by content management system 106, content management system 106can cause the document references (and corresponding metadata) on eachuser device to be deleted when performing normal synchronizationoperations.

In some embodiments, content management system 106 can send deletereferences messages 508 and 510 to user devices 230 and 310,respectively, to cause user devices 230 and 310 to delete documentreferences corresponding to document 224. For example, message 508 canidentify document reference 242 on user device 230. CMS client 234 canuse the identifier (e.g., file name, path, serial number, etc.) ofdocument reference 242 to find document reference 242 and/or metadata244 on user device 230. Once found, user device 230 can delete documentreference 242 and/or metadata 244. Similarly, message 510 can identifydocument reference 314 on user device 310. CMS client 312 can use theidentifier (e.g., file name, path, serial number, etc.) of documentreference 314 to find document reference 314 and/or metadata 316 on userdevice 230. Once found, user device 310 can delete document reference314 and/or metadata 316.

Example Processes

FIG. 6 is a flow diagram of an example process 600 for synchronizingchanges made to documents in collaboration system 222 with referencesmanaged by content management system 106. As discussed above, whenviewed by a user, document references managed by content managementsystem 106 should appear to the user as if the document references arethe documents referenced in collaboration system 222. Therefore,document references should be presented with the same metadata (e.g.,name, location, last changed timestamp, etc.) as the documentreferenced. Thus, content management system 106 and collaboration system222 should be configured to maintain synchronization of the metadata ofthe document and corresponding document references across both systems.

At step 602, a user device can receive a selection of a documentreference stored on the user device. For example, a user of user device230 can use a file browser on user device 230 to browse file system 240and view a representation of document reference 242 and/or correspondingreference metadata 244. Document reference 242 can, for example, includea unique identifier for identifying a document within collaborationsystem 222. Document reference 242 can have a file extension or filetype associated with CMS client 234. Reference metadata 244 can include,for example, a name, location, last modified timestamp, and/or othermetadata that can be presented when presenting the representation ofdocument reference 242, as described above.

At step 604, the user device can present a view of the document on thecollaboration system corresponding to the document reference on the userdevice. For example, the user can select document reference 242 on userdevice 230 to invoke collaboration client 302 on user device 230, asdescribed above. For example, user device 230 can be configured to openor invoke collaboration client 302 and/or CMS client 234 based on thefile extension and/or file type of document reference 242. Collaborationclient 302 can obtain the contents of document 224 from collaborationsystem 222 and present the contents of document 224 on a display of userdevice 230.

At step 606, the user device can receive user input modifying thedocument on the collaboration system. For example, the user can provideinput to collaboration client 302 to edit the contents of document 224on collaboration system 222. The user can provide input to collaborationclient 302 to change the name of document 224. The user can provideinput to collaboration client 302 to change the location where document224 (e.g., reference 212) is stored in the file system of the user'saccount in content management system 106.

At step 608, the user device can send the document modification to thecollaboration system. For example, collaboration client 302 can sendinformation describing the edits and/or metadata changes (e.g., namechange, location change, last modified timestamp change, etc.) tocollaboration system 222.

At step 610, the collaboration system can update the state of thedocument and/or document metadata. For example, upon receiving theinformation describing the edits and/or metadata changes for document224, collaboration system 222 can modify document 224 and/or documentmetadata 226 to reflect the edits and/or changes received fromcollaboration client 302.

At step 612, the collaboration system can send reference updateinformation to the content management system. For example, aftercollaboration system 222 updates document 224 and/or document metadata226 to reflect the edits and/or changes received from collaborationclient 302, collaboration system 222 can send a document referenceupdate message to content management system 106. The reference updatemessage can include the unique identifier for document 224 and adescription of changes made to document metadata 226.

At step 614, the content management system can update references to thedocument in the collaboration system based on the reference updateinformation. For example, upon receipt of the reference update message,content management system 106 can identify document references incontent management system 106 that refer to document 224. Contentmanagement system 106 can, for example, compare the unique identifierreceived in the reference update message to reference map 228 toidentify and/or locate document references in content management system106 that correspond to document 224. Content management system 106 canthen update the reference metadata for each identified reference toreflect the changes made to document metadata 226.

At step 616, the content management system can synchronize referencesand/or reference metadata with user devices. For example, since thedocument references and/or reference metadata are content items managedby content management system 106, content management system 106 cansynchronize the references and/or reference metadata with user devicessimilarly to other content items managed by content management system106. Thus, user device 230 can present a representation of documentreference 242 to a user that appears as if document reference 242 is thereferenced document 224 on collaboration server 220.

FIG. 7 is a flow diagram of an example process 700 for synchronizingchanges made to document references managed by content management system106 with documents in collaboration system 222. As discussed above, whenviewed by a user, document references managed by content managementsystem 106 should appear to the user as if the document references arethe documents referenced in collaboration system 222. Therefore,document references should be presented with the same metadata (e.g.,name, location, last changed timestamp, etc.) as the documentreferenced. Thus, content management system 106 and collaboration system222 should be configured to maintain synchronization of the metadata ofthe document and corresponding document references across both systems.

At step 702, a user device can receive input renaming a documentreference stored on the user device. For example, a user of user device230 can use a file browser on user device 230 to browse file system 240and view a representation of document reference 242 and/or correspondingreference metadata 244. Document reference 242 can, for example, includea unique identifier for identifying a document within collaborationsystem 222. Reference metadata 244 can include, for example, a name,location, last modified timestamp, and/or other metadata that can bepresented when presenting the representation of document reference 242on user device 230, as described above. The user can select an option inthe file browser to rename document reference 242 and can provide inputspecifying a new name for document reference 242. The file browser canrename document reference 242 on user device 230 according to the newname specified by the user.

At step 704, the user device can synchronize the modified documentreference with the user's account in the content management system. Forexample, since document reference 242 and/or reference metadata 244 arecontent items in file system 240 managed by CMS client 234 and contentmanagement system 106, CMS client 234 can automatically send informationdescribing the change (e.g., the new name) to reference 242 and/orreference metadata 244 to content management system 106 upon detecting achange to document reference 242 and/or reference metadata 244.

In some implementations, upon receiving the information describing thechange to reference 242 and/or reference metadata 244, contentmanagement system 106 can automatically update other references (e.g.,reference and/or reference metadata) to document 224 managed by contentmanagement system 106. Alternatively, content management system 106 canwait for instructions from collaboration system 222 before updatingreferences to document 224.

At step 706, the content management system can send a message to thecollaboration system to rename the document corresponding to the renameddocument reference. For example, content management system 106 candetermine that the renamed content item (e.g., document reference 242)is a reference to a document in collaboration system 222 based on thetype or extension of the content item. Based upon this determination,content management system 106 can send a message to collaboration system222 to rename the document referenced by document reference 242. Forexample, content management system 106 can obtain an identifier fordocument 224 in collaboration system 222 from document reference 242.Content management system 106 can include the document identifier andthe new name in the message sent to collaboration system 222.

At step 708, the collaboration system can rename the documentcorresponding to the renamed document reference. For example, uponreceipt of the message from content management system 106, collaborationsystem 222 can rename the document (e.g., document 224) identified bythe message according to the new name in the message. For example,collaboration system 222 can update document metadata 226 to reflect thenew name for document 224.

At step 710, the collaboration system can send reference updateinformation to the content management system. For example, aftercollaboration system 222 updates document 224 and/or document metadata226 to reflect the new name specified by the user of user device 230,collaboration system 222 can send a document reference update message tocontent management system 106. The reference update message can includethe unique identifier for document 224 and a description of changes(e.g., the new name) made to document metadata 226.

Alternatively, if content management system 106 is configured to updatereferences at step 704, collaboration system 222 may not send referenceupdate information to content management system 106 and process 700 canstop at step 708. For example, steps 712 and 714 can be performed atstep 704.

At step 712, the content management system can update references to thedocument in the collaboration system based on the reference updateinformation. For example, upon receipt of the reference update message,content management system 106 can identify document references incontent management system 106 that refer to document 224. Contentmanagement system 106 can, for example, compare the unique identifierreceived in the reference update message to reference map 228 toidentify and/or locate document references in various user accounts ofcontent management system 106 that correspond to document 224. Contentmanagement system 106 can then update the reference metadata for eachidentified reference to reflect the changes made to document metadata226.

At step 714, the content management system can synchronize referencesand/or reference metadata with user devices. For example, since thedocument references and/or reference metadata are content items managedby content management system 106, content management system 106 cansynchronize the references and/or reference metadata with user devicessimilarly to other content items managed by content management system106 so that all references to document 224 have the same name. Thus,user device 230 can present a representation of document reference 242to a user that appears as if document reference 242 is the referenceddocument 224 on collaboration server 220.

Example System Architectures

8A and FIG. 8B show example possible system embodiments. The moreappropriate embodiment will be apparent to those of ordinary skill inthe art when practicing the present technology. Persons of ordinaryskill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 8A illustrates a conventional system bus computing systemarchitecture 800 wherein the components of the system are in electricalcommunication with each other using a bus 805. Example system 800includes a processing unit (CPU or processor) 810 and a system bus 805that couples various system components including the system memory 815,such as read only memory (ROM) 820 and random access memory (RAM) 825,to the processor 810. The system 800 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 810. The system 800 can copy data from the memory815 and/or the storage device 830 to the cache 812 for quick access bythe processor 810. In this way, the cache can provide a performanceboost that avoids processor 810 delays while waiting for data. These andother modules can control or be configured to control the processor 810to perform various actions. Other system memory 815 may be available foruse as well. The memory 815 can include multiple different types ofmemory with different performance characteristics. The processor 810 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 832, module 2 834, and module 3 836 stored instorage device 830, configured to control the processor 810 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 810 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 800, an inputdevice 845 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 835 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 800. The communications interface840 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 830 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 825, read only memory (ROM) 820, andhybrids thereof.

The storage device 830 can include software modules 832, 834, 836 forcontrolling the processor 810. Other hardware or software modules arecontemplated. The storage device 830 can be connected to the system bus805. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 810, bus 805, display 835, and soforth, to carry out the function.

FIG. 8B illustrates a computer system 850 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 850 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 850 can include a processor810, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 810 cancommunicate with a chipset 860 that can control input to and output fromprocessor 810. In this example, chipset 860 outputs information tooutput 865, such as a display, and can read and write information tostorage device 870, which can include magnetic media, and solid statemedia, for example. Chipset 860 can also read data from and write datato RAM 875. A bridge 880 for interfacing with a variety of userinterface components 885 can be provided for interfacing with chipset860. Such user interface components 885 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 850 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 860 can also interface with one or more communication interfaces890 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 810 analyzing data stored in storage 870 or 875.Further, the machine can receive inputs from a user via user interfacecomponents 885 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 810.

It can be appreciated that example systems 800 and 850 can have morethan one processor 810 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware modules, alone or in combination with other devices. In anembodiment, a software module can be software that resides in memory ofa client device and/or one or more servers of a content managementsystem and perform one or more functions when a processor executes thesoftware associated with the module. The memory can be a non-transitorycomputer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

What is claimed is:
 1. A method comprising: receiving, by a contentmanagement system, a first message from a collaboration system, thefirst message including document metadata corresponding to a documentgenerated and managed by the collaboration system; storing, in thecontent management system, a document reference to the document incontent storage, wherein the document reference is managed by thecontent management system; in response to receiving the first message,saving, in the content management system, the document metadata receivedin the first message as reference metadata for the document reference;synchronizing, by the content management system, the document referenceand the reference metadata with a first local file system of a firstclient device; detecting, by the content management system, that thefirst client device shared the document reference with a second clientdevice; based on the detecting, storing, by the content managementsystem, a second document reference to the document and a secondreference metadata in the content storage; monitoring, by the contentmanagement system, the first local file system of the first clientdevice for changes made locally to the document reference; and upondetecting a change by the first client device to the document reference,synchronizing the change with the second document reference in a secondlocal file system of the second client device and with the documentmanaged by the collaboration system.
 2. The method of claim 1, furthercomprising: storing, by the content management system, a mapping of afirst identifier for the document to a plurality of document references,the plurality of document references including the document reference;in response to receiving the first message, comparing, by the contentmanagement system, a second identifier received in the first message tothe first identifier in the mapping; determining, by the contentmanagement system, that the first message includes metadata for thedocument reference based on the comparison; and in response todetermining that the first message includes metadata for the documentreference, updating, by the content management system, the metadata forthe document reference managed by the content management system.
 3. Themethod of claim 2, wherein the plurality of document references includesa third reference, and further comprising: determining, by the contentmanagement system, that the first message includes metadata for thethird reference based on the comparison; and in response to determiningthat the first message includes metadata for the third reference,updating, by the content management system, the metadata for the thirdreference managed by the content management system.
 4. The method ofclaim 3, wherein the document reference corresponds to a first useraccount of the content management system and the third referencecorresponds to a third user account of the content management systemthat is distinct from the first account.
 5. The method of claim 1,further comprising: receiving, by the content management system from afirst user device, a second message including metadata corresponding tothe document reference managed by the content management system;updating, by the content management system, metadata corresponding tothe document reference managed by the content management system based onthe metadata in the second message; and sending, by the contentmanagement system, a third message including a document identifier forthe document in the collaboration system corresponding to the documentreference and the reference metadata, where the collaboration systemupdates metadata for the document in the collaboration systemcorresponding to the identifier based on the metadata received in thethird message.
 6. The method of claim 1, where the content managementsystem and the collaboration system are distinct systems.
 7. Anon-transitory computer-readable medium including one or more sequencesof instructions that, when executed by one or more processors of acontent management system, causes: receiving, by a content managementsystem, a first message from a collaboration system, the first messageincluding document metadata corresponding to a document generated andmanaged by the collaboration system; storing, in the content managementsystem, a document reference to the document in content storage, whereinthe document reference is managed by the content management system; inresponse to receiving the first message, saving, in the contentmanagement system, the document metadata received in the first messageas reference metadata for the document reference; synchronizing, by thecontent management system, the document reference and the referencemetadata with a first local file system of a first client device;detecting, by the content management system, that the first clientdevice shared the document reference with a second client device; basedon the detecting, storing, by the content management system, a seconddocument reference to the document and a second reference metadata inthe content storage; monitoring, by the content management system, thefirst local file system of the first client device for changes madelocally to the document reference; and upon detecting a change by thefirst client device to the document reference, synchronizing the changewith the second document reference in a second local file system of thesecond client device and with the document managed by the collaborationsystem.
 8. The non-transitory computer-readable medium of claim 7,further comprising: storing, by the content management system, a mappingof a first identifier for the document to a plurality of documentreferences, the plurality of document references including the documentreference; in response to receiving the first message, comparing, by thecontent management system, a second identifier received in the messageto the first identifier in the mapping; determining, by the contentmanagement system, that the first message includes metadata for thedocument reference based on the comparison; and in response todetermining that the first message includes metadata for the documentreference, updating, by the content management system, the metadata forthe document reference managed by the content management system.
 9. Thenon-transitory computer-readable medium of claim 8, wherein theplurality of document references includes a third reference, and furthercomprising: determining, by the content management system, that thefirst message includes metadata for the third reference based on thecomparison; and in response to determining that the first messageincludes metadata for the third reference, updating, by the contentmanagement system, the metadata for the third reference managed by thecontent management system.
 10. The non-transitory computer-readablemedium of claim 9, wherein the document reference corresponds to a firstuser account of the content management system and the third referencecorresponds to a third user account of the content management systemthat is distinct from the first account.
 11. The non-transitorycomputer-readable medium of claim 7, further comprising: receiving, bythe content management system from a first user device, a second messageincluding metadata corresponding to the document reference managed bythe content management system; updating, by the content managementsystem, metadata corresponding to the document reference managed by thecontent management system based on the metadata in the second message;and sending, by the content management system, a third message includinga document identifier for the document in the collaboration systemcorresponding to the document reference and the reference metadata,where the collaboration system updates metadata for the document in thecollaboration system corresponding to the identifier based on themetadata received in the third message.
 12. The non-transitorycomputer-readable medium of claim 7, where the content management systemand the collaboration system are distinct systems.
 13. A contentmanagement system comprising: one or more processors; and a memoryhaving programming instructions stored thereon, which, when executed bythe one or more processors, performs one or more operations, comprising:receiving a first message from a collaboration system, the first messageincluding document metadata corresponding to a document generated andmanaged by the collaboration system; storing a document reference to thedocument in content storage, wherein the document reference is managedby the content management system; in response to receiving the firstmessage, saving the document metadata received in the first message asreference metadata for the document reference; synchronizing thedocument reference and the reference metadata with a first local filesystem of a first client device; detecting that the first client deviceshared the document reference with a second client device; based on thedetecting, storing a second document reference to the document and asecond reference metadata in the content storage; monitoring the firstlocal file system of the first client device for changes made locally tothe document reference; and upon detecting a change by the first clientdevice to the document reference, synchronizing the change with thesecond document reference in a second local file system of the secondclient device and with the document managed by the collaboration system.14. The content management system of claim 13, wherein the one or moreoperations further comprise: storing a mapping of a first identifier forthe document to a plurality of document references, the plurality ofdocument references including the document reference; in response toreceiving the first message, comparing a second identifier received inthe message to the first identifier in the mapping; determining that thefirst message includes metadata for the document reference based on thecomparison; and in response to determining that the first messageincludes metadata for the document reference, updating the metadata forthe document reference managed by the content management system.
 15. Thecontent management system of claim 14, wherein the plurality of documentreferences includes a third reference, and the one or more operationsfurther comprise: determining that the message includes metadata for thethird reference based on the comparison; and in response to determiningthat the first message includes metadata for the third reference,updating the metadata for the third reference managed by the contentmanagement system.
 16. The content management system of claim 15,wherein the document reference corresponds to a first user account ofthe content management system and the third reference corresponds to athird user account of the content management system that is distinctfrom the first account.
 17. The content management system of claim 14,wherein the one or more operations further comprise: receiving, from afirst user device, a second message including metadata corresponding tothe document reference managed by the content management system;updating metadata corresponding to the document reference managed by thecontent management system based on the metadata in the message; andsending a third message including a document identifier for the documentin the collaboration system corresponding to the document reference andthe reference metadata, where the collaboration system updates metadatafor the document in the collaboration system corresponding to theidentifier based on the metadata received in the third message.
 18. Thecontent management system of claim 14, where the content managementsystem and the collaboration system are distinct systems.